• 专利附录
  • 专利说明
  • 权利要求
  • 类似技术
  • 同族专利
  • 引用文献
  • 法律状态
  • 优先权
    • 专利摘要:
    PREVENTION OF REDUNDANT DISPLAY OF A NOTIFICATION ON MULTIPLE USER DEVICES. The present invention relates to a user having multiple devices who can receive notifications on each device. When it is determined that a first device is in an active state and that a notification has been viewed on that device, an indication that the notification has been viewed can be communicated by the first device to a synchronization server. It can then be determined whether the displayed notification is also present on one or more of the other user devices. Based on the determination, an indication that the notification has been viewed can be sent from the synchronization server to each of the user devices on which the notification is present. Upon receipt of the indication from the synchronization server, the displayed notification can be removed from each of the devices, thus avoiding a redundant display of the notification on multiple devices.
    公开号:BR102013015309B1
    申请号:R102013015309-5
    申请日:2013-05-31
    公开日:2020-12-15
    发明作者:Imran Chaudhri；Stephen Lemay；Caroline Cranfill；Ron Huang
    申请人:Apple Inc；
    IPC主号:
    专利说明:

    Background
    [0001] This description generally refers to the management of notifications that are presented on multiple devices of a user.
    [0002] It has become common for people to use multiple electronic devices. For example, a single user can use a mobile phone, a tablet-like computing device, a laptop-like computing system, and a desktop-like computing system during an ordinary day. It has also become increasingly common to overlap in the way in which these devices are used. While mobile devices, such as mobile phones and portable music devices, were at some point used for very specific purposes, the increasing functionality, processing capabilities and connectivity of these devices has allowed them to be used in many of the same ways that a laptop or desktop computer system.
    [0003] Since a user can switch between devices during the day, each device can be configured in a similar way to allow the user to receive the same types of information through each device. For example, a user can configure each of their devices to retrieve information such as e-mail, weather updates, sports updates, and social networking messages. Based on the multiple sources from which this information is received, each device can also consolidate information so that the user can view the information from multiple sources through a single interface. In such an arrangement, the information received by applications running on a device can generate notifications that are presented through a single notification interface. Therefore, a user can easily switch between devices and view new information that is of interest. Each device can continue to receive information and generate notifications even when the device is in an inactive state (that is, it is not being actively used by the user). Therefore, upon activation, a device can display all new notifications that have been generated since the last time the device was used. Based on the overlap in the way in which the devices are used, it can be laborious for the user to navigate through overlapping notifications that they have already viewed on another device. summary
    [0004] In one embodiment, a program storage device may include instructions to make a processor receive, on a server computer system, an indication that a notification has been viewed on a user's first device. In response to the indication, one or more of the user's additional devices can be identified and an indication that the notification was viewed on the first device can be sent to the additional devices.
    [0005] In another modality, a method includes receiving a notification on a first device among the multiple associated devices. If it is subsequently determined that the first device is in an active state and that the notification was viewed on the first device, an indication that the notification was viewed on the first device and must be removed from any associated devices can be sent by the first device.
    [0006] In another embodiment, a program storage device may include instructions for causing a processor to receive multiple messages from multiple sources on a first device associated with multiple additional devices. Based on multiple messages, multiple notifications can be generated by the first device to be displayed via a common interface on the first device. It is determined that the first device is in an active state and that one of the notifications was viewed on the first device, an indication that the notification was viewed on the first device can be sent from the first device to a synchronization server computer system. . Brief Description of Drawings
    [0007] Figure 1 is a block diagram of a network architecture according to a modality; Figure 2 is a block diagram illustrating the consolidation of information obtained from multiple sources in a single notification service, according to a modality; Figure 3 is a block diagram illustrating the synchronization of active notifications on each of the multiple user devices by a server-side notification service according to a modality; Figure 4 is a flow chart illustrating an operation by which a redundant display of notifications through multiple user devices can be avoided according to one modality; Figures 5A to 5C illustrate several mechanisms by which a redundant display of a notification on multiple user devices can be avoided according to one or more modalities; Figure 6 is a block diagram illustrating an electronic device according to an embodiment. Detailed Description
    [0008] This description pertains to the management of notifications that are received on multiple user devices. In general, techniques are described for identifying a user's active device, determining that the user has viewed a notification on the active device, and removing the notification from one or more other user devices to avoid redundant views of the same notification.
    [0009] In the following description, for the sake of explanation, numerous specific details are presented in order to provide a deep understanding of the inventive concept. As part of that description, some of those drawings in the description represent structures and devices in the form of a block diagram in order to avoid obscuring the invention. In the interests of clarity, not all characteristics of an actual implementation are described in this specification. In addition, the language used in this description was selected mainly for the purposes of reading and instruction, and may not have been selected to outline or circumscribe the present inventive matter, the consultation of claims being necessary to determine such inventive matter. Reference in that description to "a modality" means that a particular feature, structure described with respect to the modality is included in at least one embodiment of the invention, and multiple references to "a modality" should not be understood as necessarily referring to the same modality .
    [00010] It will be appreciated that the development of any real implementation (as in any development project), numerous decisions must be made to achieve the specific objectives of the designer (for example, compliance with the restrictions related to the system and the business) , and that these objectives vary from one implementation to another. It will also be appreciated that such development efforts can be complex and time-consuming, but it would nonetheless be routine for those skilled in the design of synchronization services to have the benefit of this description.
    [00011] Figure 1 illustrates the network architecture 100 according to a modality. As illustrated, a plurality of networks 102 can be provided. In the context of network architecture 100, networks 102 can take any form including, but not limited to, a local area network (LAN), a light area network (WAN) such as the Internet, or a combination of local and network networks. wide area. In addition, networks 102 can use any desired technology (wired, wireless or a combination thereof) and protocol (for example, transmission control protocol, TCP).
    [00012] Coupled to networks 102 are data server computers 104 that are capable of communicating over networks 102. In the illustrated embodiment, data server 104A can represent one or more social network servers (for example, social network servers) network hosting a social networking application), 104B data server can represent one or more sports servers (for example, network servers hosting a sports application), 104C data server can represent one or more email servers (for example, example, network servers hosting an email application), and 104D data server can represent one or more weather servers (for example, network servers hosting a weather application). The listed applications running on data servers 104A through 104D should provide an example of the applications that can be hosted by such servers and should not be limiting in any way. It will be recognized that data servers 104 can host numerous different types of applications in addition to the four illustratives illustrated in figure 1.
    [00013] Coupled also to networks 102 there may be a plurality of end user devices 106. In the illustrated embodiment, end user devices 106 represent illustrative devices belonging to a single user. For example, a user can use the 106A mobile phone, 106B tablet device, 106C laptop computer system, and 106D desktop computer system. The illustrated devices should provide an example of the devices that a typical user can own and should not be limiting in any way. Additional devices or substitutes for a user may include a personal digital assistant (PDA), a personal music device, an e-book reader, television and / or any other electronic device capable of communicating over 102 networks. end user 106 can interact with data servers 104. For example, end user devices 106 can send and receive social network messages via a social network application running on social network server 104A, receive sports updates via a sports application running on the 104B sports server, sending and receiving e-mail messages and / or calendar appointments via an electronic mail application running on the 104C e-mail server, and receiving weather updates through a weather application rotating on the server 104D weather forecast. In a typical arrangement, each user device 106 may have a client side application installed on it that interfaces with the server side application that runs on the server. For example, a client-side social networking application running on device 106 can interface with a server-side social networking application running on social network server 104A to provide functionality associated with a social network account.
    [00014] Also connected to networks 102 is a synchronization server 108. Synchronization server 108 can take the form of a data server 104, but can provide a service that maintains synchronization between the devices of a user 106 that are registered for the service. An example of a synchronization service is the Apple® iCloud® service. (APPLE is a registered trademark of Apple Inc. ICLOUD is a registered trademark of Apple, Inc.). The functionality of a synchronization service running on the synchronization server 108 will be described in more detail below. In order to facilitate communication between networks 102, at least one access circuit or router 110 is optionally coupled between them.
    [00015] Figure 2 illustrates the interaction between multiple client-side applications running on one of the user devices 106 and the server-side applications running on the various data servers 104 to provide notifications to a user of the device 106. As illustrated, the client-side social networking application 205A interfaces via communication link 215A (for example, a communication link across networks 102) with server-side social networking application 210A running on server 104A to send and receive social network messages. For example, a user of device 106 can communicate a social network message to social network friends, update their social network status, and receive social network messages sent by social network friends via the client-side social networking application. 205A. Similarly, device 106 can receive sports updates via the 215B link between the 205B client-side sports application and the 210B server-side sports application running on the 104B server, send and receive emails via the 215C link between the 205C client-side email application and 210C server-side email application running on server 104C and receive weather updates and weather forecasts through the 215D link between the 205D client-side weather application and the side of the 210D server running on the 104D server. In one embodiment, new information can be pushed from a server-side application to a client-side application running on device 106 as information is received on the server-side application. In another embodiment, information can be pulled from a server-side application by the client-side application at a particular frequency. For example, a client-side application may request updated information from the server-side application every 30 minutes. In one embodiment, the update frequency can be a selectable configuration of the client side application. In another mode, information retrieval can occur regardless of the state of the device. For example, even if device 106 is in an inactive state (that is, not in active use by the device user), applications and the client side can continue to request and receive updated information.
    [00016] Rather than receiving information from each of the client-side applications running on device 106 through separate interfaces (for example, a client-side application interface), the user can choose to consolidate the information received through these client-side applications via client-side notification service 220. Client-side notification service 220 can run on device 106 as a user-level application or operating system service. A user of device 106 can choose to receive information that is retrieved by one or more client-side applications running on device 106 as a notification through a common client-side notification service interface 220. In the illustrated embodiment, the user device 106 has already connected each 205A client side social networking application, 205B client side sports application, 205C client side email application, and 205D client side weather application to the service side notification service. client 220. In one mode, each message received by any of these client-side applications will be passed to the client-side notification service 220. In another mode, the user can define (through a client or client side notification service) a subset of messages that are received by the client side application that must be ap resented as notifications via the 220 notification service. For example, a user may not want to see a notification every time a friend on the social network updates their status or comments on another social network message, but may want to see all network messages original social media communicated by friends of the social network. Similarly, the user may wish to only receive notifications for sports updates for a particular team or weather updates for a particular location. Therefore, client side notification service 220 can provide a unique interface through which the user of device 106 can quickly view the information that is most interesting to him.
    [00017] Based on the appropriate settings, the information that is received in each of the client side applications that is connected to the client side notification service 220 is communicated to the notification service 220 as indicated by arrows 225A to 225D . In one embodiment, the information is supplied to the notification service 220 upon receipt of the information by a client-side application. In another embodiment, the notification service 220 can request updated information from each of the connected client-side applications at a certain frequency. For example, notification service 220 can request new information from each of the connected client-side applications every 10 minutes. In one embodiment, the update frequency can be a selectable notification service configuration 220. As mentioned above, the information can be retrieved by the client side applications even when device 106 is in an inactive state. Similarly, retrieved information can be passed to notification service 220 even when device 206 is in an inactive state. As such, notifications can accumulate on notification service 220 when device 106 is not in use.
    [00018] Furthermore, as will be described in greater detail below, a user can install one or more of the same client side applications on multiple devices and can connect the client side applications with the 220 notification service on multiple devices. Therefore, there may be an overlap in notifications that are displayed on multiple devices. For example, the client side social application 205A running on the mobile phone 106A can retrieve the same information as the server side social application 210A as the client side social application 205A running on the laptop 106C. In order to manage the notifications that are present in the notification service 220 on each of the user devices, client side notification service 220 can be connected to the server side notification service 230 running on the synchronization server 108 .
    [00019] In one embodiment, the synchronization server 108 can provide a user account through which information can be shared between multiple devices. For example, synchronization server 108 can provide data storage and can allow each of the devices associated with a user account to retrieve data from the store. In one embodiment, the server side notification service 230 can be one of the features offered through a user account with synchronization server 108. In another embodiment, a user account on the synchronization server 108 can maintain a registration of each of the user devices 106 and, more specifically, can keep a record of each of the user devices 106 that run the client side notification service 220. Each time a notification is received at the user side notification service client 220, the notification can be shared with the server side notification service 230 by communicating the notification over networks 102 as illustrated by communication link 235. In this way, the server side notification service 230 can maintain a record of each notification that is present for each user device.
    [00020] Referring to Figure 3, a block diagram illustrates the records of active notifications on multiple user devices (160A to 106D) maintained by the server side notification service 230 running on the synchronization server 108. The devices 106A the 106D include overlapping client side applications. To continue with the example in figures 1 and 2, the 205C client-side email application and the 205D client-side sports application are installed on each of the devices 106A through 106D. The 205B client-side sports app can be installed on the 106A mobile phone, 106B tablet device and 106C laptop computer system, but not on the 106D desktop computer system. The 205A client-side social networking app can be installed on the 106A mobile phone and 106B tablet device, but not on the 106C laptop computer system or the 106D desktop computer system. Each of the devices 106A through 106D runs the client side notification service 220 to retrieve information from installed client side applications and presents the information to the user through a single interface.
    [00021] In the illustrated modality, the user connected each of the client side applications installed on each device to the client side notification service 220. Therefore, the information received by the installed client side applications can be presented as notifications 305 through client side notification service 220 on each of devices 106A through 106D.
    [00022] In the illustrated modality, notifications 305 can be displayed through notification service 220 in the order in which notifications were received. In one embodiment, this order can be based on a time stamp associated with the original information received from the server-side application. In another embodiment, the order can be based on the order in which notifications are received by notification service 220. In another embodiment, notifications can be classified based on the client side application that generated the notification. In such a modality, the order in which client-side applications are classified can be selected by the user.
    [00023] In the illustrated modality, two social network notifications (SN NT 1 and SN NOT 2) are received at notification service 220 from the 205A client-side social network application, a sports notification (SPORTS NOT 1) is received at notification service 220 of the 205B client-side sports application, two e-mail notifications (EMAIL NOT 1 and EMAIL NOT 2) are received at notification service 220 of the 205C client-side e-mail application, and a notification (WX NOT 1) is received at notification service 220 of the 205D client side weather application.
    [00024] The client side notification service 220 can only receive notifications corresponding to the client side applications that are installed on the device. For example, the client side notification service 220 running on the mobile phone 106A may display each of the notifications mentioned above since each of the client side applications 205A to D is installed on the mobile phone 106A. In contrast, the client side notification service 220 running on the 106D desktop computer can display only e-mail and weather notifications since only the 205A client-side e-mail application and the weather side application 205D client are installed on the 106D desktop computer.
    [00025] While the illustrated modality indicates that the notifications received by the client-side notification service 220 are directly linked to the client-side applications that are installed on the device, this is not necessarily the case. For example, for a particular client-side application that is installed on a first device and a second device, the user may want to receive notifications on the first device, but not on the second device. Therefore, the user can connect the client side application to the client side notification service 220 on the first device, but not on the second device. Similarly, the user can connect the client side application to the client side notification service 220 on both devices, but can use different settings so that the first device can display all messages from the client side application such as notifications via the client side notification service 220 while the second device displays only a subset of those notifications.
    [00026] Client side notification service 220 on each of devices 106A to D can communicate notifications 305 to client side notification service 230 running on synchronization server 108 over networks 102 as illustrated by the links of communication 235A to D. In one mode, the communication of a notification can occur upon receipt of the new notification by the client side notification service 220. In another mode, the communication of notifications can occur according to a certain frequency. For example, client-side notification service 220 can transmit any new notification information to server-side notification service 230 every 5 minutes. In one embodiment, the client side notification service 220 can include account credentials in any communication to the synchronization server 108. These credentials can allow the synchronization server 108 to identify a user account and the devices associated with the account of user.
    [00027] In one embodiment, the actual notification can be transmitted from the client-side notification service 220 to the server-side notification service 230. That is, the actual data that constitutes the notification can be transmitted from from client-side notification service 220 to server-side notification service 230. In another embodiment, a notification identifier can be transmitted from client-side notification service 220 to server-side notification service 230 For example, a hash algorithm can be applied to the notification and the resulting hash value can be sent to the server side notification service 230. In such an embodiment, each of the devices 106A through D can perform the same hashing algorithm. so that server side notification service 230 recognizes the resulting hash as constituting the same notification for each of the devices.
    [00028] Based on the notifications received (and / or notification identifiers), the server side notification service 230 can maintain the data store 310 to track the notifications that are present on each of the user devices. In one embodiment, data store 310 can maintain a list of any active notifications present on any of the user's registered devices. For each active notification, data store 310 can also indicate which of the user devices the notification is present on. As illustrated, redundant notifications can accumulate on each of the user's devices. Furthermore, as noted above, notifications can continue to accumulate even when a device is in an inactive state. Therefore, a user who uses the 106A mobile phone to communicate during the day and uses the 106D desktop computer to communicate at night can view various notifications on the 106A mobile phone during the day, but may have to navigate through the same notifications (which accumulated while the 106D desktop computer was inactive) when transitioning to the 106D desktop computer system at night. In one embodiment, the connection between client-side notification service 220 and server-side notification service 230 for each of the user devices can prevent redundant display of notifications.
    [00029] With reference to figure 4, operation 400 illustrates a process by which a redundant display of notifications can be avoided according to a modality. As described above, notifications can be received on multiple devices from a single user (block 405). In one embodiment, these notifications can include any type of information that is presented to a user through a common interface. For example, messages from multiple sources (for example, multiple server-side applications) can be compiled into notifications that are presented to a user through a common interface (for example, a 220 notification service interface). In addition to the illustrative notifications listed above, notifications may include voicemail messages, text messages (for example, short message service, or instant messaging service), stock exchange quote, video messages, etc. As noted above, notifications can be received on user devices even when the devices are in an inactive state. Therefore, notifications can accumulate on an inactive device to be displayed when the user activates the device and navigates to an interface through which notifications can be viewed. Although notifications received on each device may be different based on specific device settings, there may be some overlap in notifications received on devices. Therefore, the same notification can be displayed on two or more devices.
    [00030] It can be determined that one of the devices is in an active state (block 410). As used here, a device can be in an active state when a user is actively using the device. The determination of whether a device is in an active state can be made by the device itself and can occur in a variety of different ways. In one embodiment, the device can employ observation detection to determine the state of the device. In such an embodiment, an image capture component (for example, a digital camera) that is part of the device can be activated to determine whether a human face is detectable. If so, it can be determined that a user is looking at a view of the device and that the device is therefore in an active state. In another embodiment, device sensors (for example, an ambient / proximity light sensor, accelerometer and / or gyroscope) can be used to detect changes in the orientation of the device (for example, the positioning of the device). Based on certain orientations or changes in orientation, it can be determined that the device is in an active state. In another additional embodiment, it can be determined that the device is in an active state based on the transmission and / or reception of data over a network. While data can be transmitted over a device's network connection even when the device is in an idle state, certain patterns of data transmission and reception can indicate that the device is active. For example, while data can be sent and retrieved in short bursts while the device is in an idle state, transmitting or receiving data over a network over a longer period or from a specific source / destination may be indicative of an active device. In another embodiment, a device can be determined to be active based on user interaction with the device. For example, the use of a device interface such as a button, keyboard, disc, click wheel, keyboard, monitor screen and / or a touch screen, mouse, trackpad, etc. can indicate that the device is active.
    [00031] After it has been determined that a particular device is active, it can be determined that a notification was viewed on the active device by a user of the active device (block 415). The determination that a notification has been viewed can always occur in a variety of ways. In one embodiment, it can be determined with a high degree of confidence that a notification has been viewed if the user responds to the notification. For example, if the notification is a text message, it can be determined that the notification was viewed if the user responds (for example, by a reply text message) to the message sender.
    [00032] In another mode, a notification can be selected in order to allow the user to interact with the notification. Selecting the notification can cause the client-side application that generated the notification to launch in order to allow the user to interact with (for example, respond to or view a video file associated with) the notification. In such a mode, the selection of the notification may indicate that the notification has been viewed.
    [00033] In another modality, it can be determined that a notification was viewed based on the presence of the notification in a display element of the active device. In order to confidently infer that a notification has been read based on the presence of the notification on a display element of the device, the notification may be required to be present on the display element for a specified time limit. For example, the presence of a notification on a device display element for a specified number of seconds may indicate that the notification has been viewed. In one embodiment, the time limit can be based on the length of the notification (for example, the amount of text in a text message notification).
    [00034] In another additional embodiment, the accuracy of determining that a notification has been viewed based on the presence of the notification on a device display element can be improved by combining such a method with the observation detection described above and / or process guidance monitoring. For example, if it is known that a notification is being displayed on a display element of the device and that a human face is simultaneously detectable through observation detection, it can be determined with increased confidence that the notification was viewed on the active device. Likewise, it is known that a notification is being displayed on a display element of the device and that the device is positioned in a specific orientation (for example, an orientation that is indicative of a user looking at the display element), can be determined with increased confidence that the notification was viewed on the active device.
    [00035] In another embodiment, it can be determined that a notification was viewed on the active device based on a user interaction with a device's user interface in conjunction with the display of the notification on a device display element. For example, a given rolling pattern through a series of notifications can be indicative of a user viewing the notifications. For example, if multiple notifications are present on a device, and the user scrolls through the notifications and pauses when a particular notification is centered on a display element of the device, it can be determined that the notification has been viewed. The mechanisms described above for determining that a notification was viewed on a device are provided as examples and should not be limiting in any way. One skilled in the art will be aware of additional mechanisms by which it can be determined that a notification has been viewed on a device or by which confidence in such a determination can be improved.
    [00036] After it has been determined that a notification has been viewed on the device, an indication that the notification has been viewed can be sent to a synchronization server (block 420). As described above, a synchronization server can manage the notifications that are present on each of the user's devices. In one embodiment, the indication may include information to allow the synchronization server to identify the devices that are associated with the device on which the notification was viewed. In one embodiment, the indication may include the notification that has been determined to have been viewed on the active device. That is, the actual data that constitutes the notification can be sent from the active device to the synchronization server. In another embodiment, a notification identifier can be sent from the active device to the synchronization server. As described above with reference to figure 3, the identifier can be the result of a hash algorithm performed on the data that constitute the notification. It should be noted that the indication sent from the active device (block 420) differs from the indication sent from a device to the synchronization server as described in figure 3. More specifically, the trainer indicates that a notification was viewed on the active device while the latter indicates that a notification is present (but not necessarily viewed) on the device.
    [00037] Upon receipt of the indication that a notification has been viewed on one of the user devices, the synchronization server determines whether the displayed notification is present on the other devices. In one embodiment, the notification corresponding to the displayed notification is identified in the data store 310. In another embodiment, the notification can be identified in the data store 310 using the notification itself or notification identifier received in 420. Once the notification is identified in data store 310, it can then be determined whether the same notification is present on other devices that the user has registered with the synchronization server. As described above with respect to figure 3, each of the user devices can report their notifications to the synchronization server. Therefore, the synchronization server may be aware of the user devices on which the previewed notification is present. It is determined that the displayed notification is not present on any of the other user devices ("NO" in block 425), the displayed notification can simply be removed from the device on which it was viewed (block 430). In one embodiment, removal of notification can refer to removal of notification from an interface on which notifications are displayed. Therefore, the previewed notification may not be removed from the device completely. In one embodiment, the removal of the displayed notification can be done locally when it is determined that the notification was viewed on the device (block 415). In such a modality, if it is determined that the displayed notification is not present on any of the other user devices ("NO" in block 425), no response from the synchronization server may be necessary. In another embodiment, the notification may not be removed from the notification interface until an instruction to do so has been received by the device on which the notification was viewed. In this mode, the synchronization server can send a response to the device on which the notification was viewed, indicating that the notification must be removed from the notification interface (block 430).
    [00038] If it is determined that the displayed notification is present on one or more of the other user devices ("YES" in block 425), an indication that the notification has been viewed can be sent from the synchronization server to each of the user devices where the notification is present (block 435). That is, the synchronization server can push the indication to each of the devices on which the notification is present. Like the referral sent from the device on which the notification was viewed, the referral sent from the synchronization server can include the viewed notification itself or an identifier of the viewed notification. After receiving the indication that a notification has been viewed, each of the receiving devices can identify the displayed notification and can remove the notification from the interface through which the notification is displayed (block 440). Data store 310 can also be updated on the synchronization server to remove the displayed notification from a list of active notifications. Therefore, when it is determined that a notification has been viewed on one of multiple user devices, a redundant display of the same notification on one or more of the other user devices can be avoided.
    [00039] While the illustrated mode describes the identification of each of the user devices on which the displayed notification is present (block 425), this step is not strictly necessary. In an alternative embodiment, the synchronization server, regardless of the devices on which a notification is present, can simply send an indication that a notification has been viewed for all registered user devices. In such a modality, a device receiving such an indication will determine whether the displayed notification is present on the device (for example, it is present on an interface through which notifications are displayed). If so, the device can remove the notification as it has already been viewed on another device. If not, the device can simply disregard the indication of the synchronization server.
    [00040] Figures 5A to 5C illustrate several mechanisms by which a redundant display of a notification on multiple user devices can be avoided. Referring first to Figure 5A, the client side application 205 on each of the devices 106A to C receives a message from the corresponding server side application 210 running on the data server 104 (505). As described above, the client-side application 205 for each of the devices 106A to C can be configured to retrieve new information from the corresponding server-side application 210 at a given frequency. Based on the predefined settings (for example, notification settings) on each of the devices 106A through C, the information retrieved by the client side application 205 can be passed to the client side notification service 220 to be displayed as a notification on each of devices 106A to C (510). As further described above, notification can be communicated from client side notification service 220 to server side notification service 230 running on synchronization server 108 (515). The server-side notification service 230 can therefore maintain a record indicating that notification is present on each of devices 106A through C. Although operations 505, 510 and 515 are grouped, it should be noted that operations can be specific to each particular device and can occur at different times.
    [00041] At some point, it can be determined that device 106B is in an active state and that the notification has been viewed on device 106B. Based on the determination that the notification was viewed on device 106B, an indication that the notification was viewed can be sent from client side notification service 220 running on device 106B to server side notification service 230 being executed on the synchronization server 108 (520). In response to the indication that the notification was viewed on the device 106B, the server side notification service 230 may determine that the notification is present on each of the devices 106A to C and may send an indication to the side notification service of client 220 on each of the devices 106A to C that the notification was viewed (525). While the illustrated mode presents a communication for each of the devices in which the notification is present, in an alternative mode, the indication may not be sent to device 106B since device 106B is already aware of the notification display. The notification can therefore be removed from a notification interface of the client side notification service 220 for each of the devices on which the notification is present to avoid a redundant display of the notification on multiple devices.
    [00042] In an alternative embodiment illustrated in figure 5B, the information retrieved by the client side application 205 may result in the generation of a notification on each of the devices 106A to C in the same way as described with respect to figure 5A. In the embodiment illustrated in Figure 5B, however, client-side notification service 220 may not report the presence of notification for server-side synchronization service 230 running on synchronization server 108. In fact, despite the synchronization server 108 is shown for comparison purposes, it may not be used in the embodiment of figure 5B.
    [00043] In the same way as described above, it can be determined that device 106B is in an active state and that the notification has been viewed on device 106B. However, instead of transmitting the indication that the notification has been viewed to the synchronization server 108, the client side notification service 220 transmits the notification to the server side application 210 that is responsible for generating the notification ( 530) (that standing, the server side application from which the information that resulted in the notification was retrieved). Although the client-side notification service 220 is illustrated as communicating the referral directly to the server-side application 210, the referral can actually be relayed to the server-side application 210 through the client-side application 205 In one embodiment, the statement may contain information (for example, credentials) that identifies a user account with the server-side application. In such an embodiment, the user account can be used to maintain a record of user devices (eg 106A to C) that are associated with the account. In one embodiment, the indication may include the notification or a notification identifier that allows the server-side application 210 to identify the message that corresponds to the displayed notification.
    [00044] In response to receiving the indication, the server side application 210 can send an indication to each of the client side applications 205 on each of the devices 106A to C that the notification has been viewed (535). In one embodiment, the indication that the notification has been viewed can be pushed to each of the devices 106A to C. In another embodiment, the indication can be communicated to each of the devices 106A to C when the client-side application 205 recovers. the server-side application information (for example, according to a certain update schedule). The indication can then be passed from the client side application 205 to each of the devices 106A to C to the client side notification server 220 to each of the devices 106A to C (540) to make the notification service client side 220 remove the notification and avoid a redundant display of the notification on multiple devices.
    [00045] In the embodiment of figure 5B, the server-side application 210 can function similarly to the server-side notification service 230 in that it can maintain a record of the devices associated with a particular user (or a particular user account) ). For example, each client side application case 205 may register with server side application 210 to communicate information associated with the application. Therefore, server-side application 210 may have a listing of the client-side applications (and corresponding devices) that are associated with a user account. It should be noted, however, that while the server-side notification service 230 can manage notifications for multiple sources (that is, notifications that originated as information retrieved from multiple server-side applications), the application server side 210 of the modality illustrated in figure 5B can manage only those notifications that were generated based on the information that was provided. Therefore, server-side notification service 230 can be described as a global notification manager while server-side application 210 of Figure 5B can be described as an application-specific notification manager.
    [00046] In another modality illustrated in figure 5C, information can be received (505), a generated notification (510), the presence of the communicated notification (515), and an indication that the notification was viewed communicated (520) from as described in figure 5A. However, in response to the indication that the notification has been viewed, server-side notification service 230 can send an indication to the client-side application 205 that caused the notification to be generated instead of directly to the service client side notification 220 (545). The client-side application 205 for each of the devices 106A to C can then have the notification removed from notification service 220 (550). Therefore, instead of communicating the indication that the notification was viewed directly to the client-side notification service 220, the indication can be communicated to the application that caused the notification to be generated (that is, application-side application). 205) so that the application can have the notification removed. The modalities of figures 5A to 5C illustrate different mechanisms for achieving the common objective to avoid redundant display of a notification on multiple devices.
    [00047] With reference to figure 6, a simplified functional block diagram of an illustrative electronic device 600 is illustrated according to an embodiment. Electronic device 600 may include processor 605, monitor 610, user interface 615, graphics hardware 620, device sensors 625 (e.g. proximity sensor / ambient light sensor, accelerometer and / or gyroscope), microphone 630, codec audio (s) 635, speakers 655, memory 660, storage 665, and communications bus 670. The electronic device 600 can be, for example, a personal digital assistant (PDA), a personal music device, a mobile phone , a notebook, a laptop or tablet computer system, a desktop computer system, or a server computer system. More particularly, any of the devices 106, data servers 104, and synchronization server 108 can take the form of an electronic device 600.
    [00048] Processor 605 can execute instructions necessary to perform or control the operation of many functions performed by device 600. Processor 605 can, for example, trigger display 610 and receive user registration from user interface 615. The interface user interface 615 can take a variety of forms, such as a button, keyboard, dial, click wheel, keyboard, display screen and / or a touch screen. The 605 processor can also, for example, be a chip system such as that found on mobile devices and include a dedicated graphics processing unit (GPU). The 605 processor may be based on reduced instruction set computer (RISC) or complex instruction set computer (CISC) architectures or any other suitable architecture and may include one or more processing cores. Graphics hardware 620 may be special purpose computing hardware for graphics processing and / or assistant processor 605 for processing graphics information. In one embodiment, the graphics hardware 620 may include a programmable graphics processing unit (GPU).
    [00049] The camera and sensor circuit assembly 650 can capture still and video images that can be processed, at least in part, by the 655 video codec (s) and / or the 605 processor and / or graphics hardware 620, and / or a dedicated image processing unit built into circuitry 650. Images captured in this way can be stored in memory 660 and / or in storage 665. Memory 660 can include one or more different types of media used by the processor 605 and graphics hardware 620 to perform the functions of the device. For example, memory 660 may include a temporary memory store, read-only memory (ROM) and / or a random access memory (RAM). The 665 can store media (for example, audio, image and video files), instructions or computer program software, preference information, device profile information and any other suitable data. The 665 storage can include one or more non-transitory storage media including, for example, magnetic disks (fixed, floppy and removable) and tape, optical media such as CD-ROMs and digital video discs (DVDs), and memory devices semiconductors such as Electrically Programmable Read Only Memory (EPROM), and Electrically Programmable and Erasable Read Only Memory (EEPROM). Memory 660 and storage 665 can be used to tangibly retain computer program instructions or code organized into one or more modules and written in any desired computer programming language. When executed, for example, by processor 605, such computer program code may implement one or more of the methods described here.
    [00050] It should be understood that the description above should be illustrative, not restrictive. The material has been presented to allow anyone skilled in the art to create and use the inventive concepts described here, and is provided in the context of particular modalities, variations of which will be readily apparent to those skilled in the art (for example, some of the described modalities may be used in combination with each other). Many other modalities will be apparent to those skilled in the art upon review of the above description. The scope of the invention, therefore, must be maintained with reference to the appended claims, together with the full scope of the equivalences to which such claims are entitled. In the appended claims, the terms "including" and "in which" are used as simple English equivalences of the respective terms "comprising" and "where".
    权利要求:
    Claims (20)
    [0001]
    1. Non-transitory program storage device, readable by a processor and characterized by the fact that it comprises instructions stored in it to make the processor: identify, by a server computer system, a plurality of associated devices, in which the computer server system tracks notifications that are present in the plurality of associated devices; receiving, in the server computer system, a first indication from a first device of the plurality of associated devices that a first notification was received by the first device; update, in the server computer system, a record of which notifications are present in which of the various associated devices, based on the first indication of information; receives, in the server computer system, a second indication of information from the first device that a second notification is received by the first device; update, in the server computer system, the record of which notifications are present in which of the various associated devices, based on the second information indication; receive, on the server computer system, a first indication that the first notification was viewed on the first device, where the first notification is associated with a first application on the first device; receive, on the server computer system, a second indication that the second notification was viewed on the first device, where the second notification is associated with a second application on the first device; identify, by the server computer system, one or more additional devices from the plurality of associated devices that present the first and second notifications based on the record of which notifications are present in which plurality of associated devices; send, through the server computer system, a third indication that the first notification was viewed on at least one of the one or more devices identified; and send, through the server computer system, a fourth indication that the notification has been viewed for at least one or more additional user devices.
    [0002]
    2. Non-transitory program storage device according to claim 1, characterized by the fact that the instructions for making the processor receive the first indication that the notification was viewed on the first device comprise instructions for making the processor processor receives a notification identifier.
    [0003]
    3. Non-transitory program storage device, according to claim 2, characterized by the fact that the identification of the notification comprises a result of a hash algorithm applied to the notification.
    [0004]
    4. Non-transitory program storage device according to claim 2, characterized by the fact that it still comprises instructions to make the processor identify the notification in a data store of the server computer system using the notification identifier.
    [0005]
    5. Non-transitory program storage device according to claim 1, characterized by the fact that the instructions to make the processor receive the first indication that the notification was viewed on the first device comprise instructions to make the processor processor receives credentials associated with a user account.
    [0006]
    6. Non-transitory program storage device according to claim 5, characterized in that the instructions for making the processor identify one or more additional user devices comprise instructions for making the processor identify one or more additional devices that are associated with the account.
    [0007]
    7. Non-transitory program storage device, according to claim 1, characterized by the fact that it still comprises instructions that make the processor determine if the notification is present in any one or more additional user devices.
    [0008]
    8. Non-transitory program storage device according to claim 7, characterized by the fact that the instructions to have the processor send the second indication that the notification has been viewed for at least one of one or more additional devices User instructions include instructions to have the processor send the second indication to only the devices on one or more additional user devices on which the notification is present.
    [0009]
    9. Method, characterized by the fact that it comprises the steps of: receiving, by a processor of a first device from a plurality of associated devices, of a notification; determine, by the processor of the first device, that the first device is in an active state; determining, by the processor of the first device, that the notification was viewed on the first device by a user of the first device; and sending, by the processor of the first device, an indication that the notification was viewed on the first device and must be removed from any of the plurality of associated devices on which the notification is present.
    [0010]
    10. Method according to claim 9, characterized in that the step of determining that the first device is in an active state comprises the detection, by an image capture component of the first device, of a human face.
    [0011]
    11. Method according to claim 9, characterized in that the step of determining that the first device is in an active state comprises identifying, by one or more sensors of the first device, of an orientation of the first device.
    [0012]
    12. Method according to claim 11, characterized in that the step of determining that the first device is in an active state comprises detecting, by one or more sensors, a change in the orientation of the first device.
    [0013]
    13. Method according to claim 9, characterized by the fact that the step of determining that the notification was viewed on the first device comprises determining, by the processor of the first device, that the notification was displayed on a display element of the first device.
    [0014]
    14. Method according to claim 13, characterized in that the step of determining that the notification was displayed on a display element of the first device comprises determining, by the processor of the first device, that the notification was displayed on the element for more than a certain time limit.
    [0015]
    15. Method, according to claim 13, characterized by the fact that the step of determining that the notification was viewed on the first device still comprises identifying, by one or more sensors of the first device, of an orientation of the first device.
    [0016]
    16. Non-transitory program storage device, readable by a processor and characterized by the fact that it comprises instructions stored in it to make the processor: receive, in a first device among a plurality of associated devices, a plurality of messages from a plurality of sources; manages, by the first device, a plurality of notifications based on the plurality of messages, the plurality of notifications to be displayed through a common interface of the first device; determine, by the first device, that the first device is in an active state; determines, by the first device, that one of the plurality of notifications was viewed in a display element of the first device; and send, through the first device, an indication that the notification was viewed on the first device to a synchronization server computer system.
    [0017]
    17. Non-transitory program storage device according to claim 16, characterized in that the instructions for making the processor generate the plurality of notifications comprise instructions for making the processor determine whether one or more of them plurality of messages satisfy a predefined condition to be presented as a notification.
    [0018]
    18. Non-transitory program storage device according to claim 16, characterized in that the instructions for making the processor generate the plurality of notifications to be presented through the common interface comprise instructions for making the processor manages notifications to be displayed through a client-side notification service interface on the first device.
    [0019]
    19. Non-transitory program storage device according to claim 18, characterized by the fact that the notification service comprises a service of an operating system of the first device.
    [0020]
    20. Non-transitory program storage device, according to claim 18, characterized by the fact that the instructions to have the processor send the indication that the notification was viewed on the first device comprise instructions that cause the service client-side notification system send the referral to a server-side notification service running on the synchronization server computer system.
    类似技术:
    公开号 | 公开日 | 专利标题
    BR102013015309B1|2020-12-15|non-transitory storage device and method
    US10785597B2|2020-09-22|System to track engagement of media items
    AU2012273440B2|2015-11-26|Using photographs to manage groups
    JP2017215995A|2017-12-07|Modulation of visual notification parameters based on message activity and notification value
    US20160089089A1|2016-03-31|Systems and methods for digital predictive disease exacerbation and pre-emptive treatment
    US20140214950A1|2014-07-31|Adding user to logical group based on content
    US10387539B2|2019-08-20|Digital card management with style-based dynamic card generation
    GB2558035A|2018-07-04|Detecting extraneous social media messages
    EP3235272A1|2017-10-25|Contextually aware dynamic group formation
    US20200014652A1|2020-01-09|Message Data Transfer
    US11282032B2|2022-03-22|Avoiding a redundant display of a notification on multiple user devices
    US11275439B2|2022-03-15|Sleep detection in a location sharing system
    US10936066B1|2021-03-02|Sleep detection in a location sharing system
    AU2015224489B2|2017-09-07|Dynamic duty-cycling of processor of mobile device based on operating condition of mobile device
    US20160359971A1|2016-12-08|Method and system for tracking information transfer between devices
    KR101630136B1|2016-06-13|Organization of inputs for online service
    同族专利:
    公开号 | 公开日
    CN103559022B|2017-04-19|
    AU2013205552B2|2015-12-17|
    CN107203384A|2017-09-26|
    KR101568901B1|2015-11-12|
    CN107203384B|2021-06-01|
    KR20130135140A|2013-12-10|
    US10210480B2|2019-02-19|
    CN103559022A|2014-02-05|
    US20190138992A1|2019-05-09|
    AU2013205552A1|2013-12-19|
    EP2669854A1|2013-12-04|
    JP2013250973A|2013-12-12|
    BR102013015309A2|2015-08-11|
    US20130325922A1|2013-12-05|
    JP5852988B2|2016-02-09|
    引用文献:
    公开号 | 申请日 | 公开日 | 申请人 | 专利标题
    JP3453459B2|1995-06-19|2003-10-06|キヤノン株式会社|E-mail system and control method thereof, and communication terminal device and control method thereof|
    US6983308B1|1998-11-19|2006-01-03|Openwave Systems, Inc.|Mail synchronization of remote and local mail systems|
    JP3476391B2|1999-08-18|2003-12-10|株式会社デジタル|Programmable display device|
    DE60129434T2|2000-03-16|2008-04-17|Microsoft Corp., Redmond|GENERATION AND MANAGEMENT OF PRIORITIES|
    JP2001290737A|2000-04-04|2001-10-19|Reudo Corp|Device and method for exchanging data between portable telephone set and computer|
    JP2002132632A|2000-10-25|2002-05-10|Fuji Xerox Co Ltd|Device, system and method for reading fee management, and computer-readable recording medium|
    JP2002207632A|2001-01-12|2002-07-26|Fujitsu Ltd|Shared information processing system and recording medium|
    JP3753244B2|2002-11-27|2006-03-08|日本電気株式会社|Real-time web sharing system|
    US7496630B2|2003-05-06|2009-02-24|At&T Intellectual Property I, L.P.|Adaptive notification delivery in a multi-device environment|
    US7565425B2|2003-07-02|2009-07-21|Amazon Technologies, Inc.|Server architecture and methods for persistently storing and serving event data|
    US8627489B2|2003-10-31|2014-01-07|Adobe Systems Incorporated|Distributed document version control|
    US7925754B2|2003-11-21|2011-04-12|Microsoft Corporation|Method and computer program product to provide synch notifications to client devices|
    US8356317B2|2004-03-04|2013-01-15|Sharp Laboratories Of America, Inc.|Presence based technology|
    US7809682B2|2004-05-24|2010-10-05|Apple Inc.|Data synchronization between multiple devices|
    US7814231B2|2004-05-24|2010-10-12|Apple Inc.|Method of synchronizing between three or more devices|
    US7305069B1|2004-07-20|2007-12-04|Cisco Technology, Inc.|Multi-copy, multi-media, non-redundant messaging|
    US7970823B2|2004-09-02|2011-06-28|Broadway Technology, Llc|System for sharing data objects among applications|
    US7702730B2|2004-09-03|2010-04-20|Open Text Corporation|Systems and methods for collaboration|
    US7475395B2|2005-01-04|2009-01-06|Nokia Corporation|Multiple device notification synchronization|
    JP2007102301A|2005-09-30|2007-04-19|Nec Personal Products Co Ltd|Mail-synchronizing method and mail-synchronizing device|
    US20070143435A1|2005-12-15|2007-06-21|Bellsouth Intellectual Property Corporation|Presentation of Un-Viewed Messages|
    WO2007113836A2|2006-04-03|2007-10-11|Beinsync Ltd.|Peer to peer syncronization system and method|
    US7907051B2|2006-06-13|2011-03-15|Microsoft Corporation|Techniques for setting and indicating presence for a device|
    US8126443B2|2006-06-13|2012-02-28|Microsoft Corporation|Auxiliary output device|
    US20080005238A1|2006-06-29|2008-01-03|Microsoft Corporation|Roaming consistent user representation information across devices and applications|
    US20090248806A1|2006-07-19|2009-10-01|Ari Teman|System and method for dynamically changing item status in static email messages|
    US20080059656A1|2006-08-31|2008-03-06|Saliba Bassam A|Content synchronization among associated computing devices|
    US8238882B2|2006-10-19|2012-08-07|Research In Motion Limited|System and method for storage of electronic mail|
    CN101257375B|2006-12-31|2012-08-08|华为技术有限公司|Method and device for realizing multi-terminal message synchronization|
    US8600120B2|2008-01-03|2013-12-03|Apple Inc.|Personal computing device control using face detection and recognition|
    US8090767B2|2008-01-07|2012-01-03|Apple Inc.|Pairing and storage access scheme between a handheld device and a computing system|
    US7890591B2|2008-01-31|2011-02-15|International Business Machines Corporation|Method for an efficient electronic messaging system|
    US7747784B2|2008-03-04|2010-06-29|Apple Inc.|Data synchronization protocol|
    US8019863B2|2008-03-28|2011-09-13|Ianywhere Solutions, Inc.|Synchronizing events between mobile devices and servers|
    US8645376B2|2008-05-02|2014-02-04|Salesforce.Com, Inc.|Method and system for managing recent data in a mobile device linked to an on-demand service|
    US8812614B2|2008-06-05|2014-08-19|Qualcomm Incorporated|Data backup for a mobile computing device|
    KR20110037969A|2008-06-25|2011-04-13|톰슨 라이센싱|Targeted user notification of messages in a monitoring system|
    US8135670B2|2008-07-22|2012-03-13|International Business Machines Corporation|Embedded change logging for data synchronization|
    JP5066497B2|2008-09-09|2012-11-07|富士フイルム株式会社|Face detection apparatus and method|
    US20100107164A1|2008-10-24|2010-04-29|Oskari Koskimies|Method, System, and Apparatus for Process Management|
    US8965920B2|2008-12-15|2015-02-24|Verizon Patent Licensing Inc.|Distributing and sharing content in a network|
    US8904292B2|2008-12-31|2014-12-02|Motorola Mobility Llc|Method and system for processing electronic mail|
    CN102282873B|2009-01-19|2014-06-11|Lg电子株式会社|Method for delivering cpm message and server thereof|
    US8392543B1|2009-01-30|2013-03-05|Sprint Communications Company L.P.|Synchronization of content change across multiple devices|
    US8538815B2|2009-02-17|2013-09-17|Lookout, Inc.|System and method for mobile device replacement|
    US8064896B2|2009-03-09|2011-11-22|Apple Inc.|Push notification service|
    US8700776B2|2009-03-23|2014-04-15|Google Inc.|System and method for editing a conversation in a hosted conversation system|
    US20100257451A1|2009-04-05|2010-10-07|Hbr Labs Inc.|System and method for synchronizing collaborative web applications|
    EP2242258A1|2009-04-16|2010-10-20|Panasonic Corporation|Content access notification|
    US8350694B1|2009-05-18|2013-01-08|Alarm.Com Incorporated|Monitoring system to monitor a property with a mobile device with a monitoring application|
    JP5360978B2|2009-05-22|2013-12-04|株式会社日立製作所|File server and file operation notification method in file server|
    US8527602B1|2009-05-28|2013-09-03|Google Inc.|Content upload system with preview and user demand based upload prioritization|
    US8255571B2|2009-06-30|2012-08-28|Apple Inc.|Updating multiple computing devices|
    US20110010629A1|2009-07-09|2011-01-13|Ibm Corporation|Selectively distributing updates of changing images to client devices|
    US8842815B2|2009-07-29|2014-09-23|Comcast Cable Communications, Llc|Identity management and service access for local user group based on network-resident user profiles|
    WO2011040774A2|2009-09-30|2011-04-07|Samsung Electronics Co., Ltd.|System and method of handling read and delivery confirmations for messages|
    US8858313B1|2010-01-25|2014-10-14|Topspin Networks, Inc.|Methods, systems, and devices for synchronized parallel gameplay|
    JP5682996B2|2010-02-04|2015-03-11|インターナショナル・ビジネス・マシーンズ・コーポレーションＩｎｔｅｒｎａｔｉｏｎａｌ Ｂｕｓｉｎｅｓｓ Ｍａｃｈｉｎｅｓ Ｃｏｒｐｏｒａｔｉｏｎ|Client program, terminal, server device, server program, system and method|
    BR112012017687A2|2010-02-12|2016-04-05|Thomson Licensing|method for playing synced content|
    US10455275B2|2010-02-16|2019-10-22|Comcast Cable Communications, Llc|Disposition of video alerts and integration of a mobile device into a local service domain|
    US8799349B2|2010-02-18|2014-08-05|Blackberry Limited|Method, system and apparatus for propagating data change notifications|
    US8433797B2|2011-04-11|2013-04-30|Ringcentral, Inc.|User interface for accessing messages|
    US8407181B2|2010-05-26|2013-03-26|Research In Motion Limited|Email system providing enhanced conversation and category search features and related methods|
    US9380011B2|2010-05-28|2016-06-28|Google Inc.|Participant-specific markup|
    EP2400445A3|2010-06-28|2012-05-23|Samsung Electronics Co., Ltd.|Image device, receiving method of contents, server and providing method of contents|
    US8463859B2|2010-07-02|2013-06-11|Research In Motion Limited|Email system including synchronization server providing synchronization based upon synchronization indicators stored on mobile devices and related methods|
    US8812607B2|2010-08-23|2014-08-19|Maxxess Systems, Inc.|Private mobile messaging and data communications apparatus and method of managing organizational messaging|
    US8725682B2|2010-09-08|2014-05-13|Daniel J Young|Distribution and synchronization of digital objects|
    US8478905B2|2010-10-01|2013-07-02|At&T Intellectual Property I, Lp|System for synchronizing to a mobile device server|
    US20120110595A1|2010-10-28|2012-05-03|Michael Reitman|Methods and systems for managing concurrent design of computer-aided design objects|
    US20120117105A1|2010-11-05|2012-05-10|Apple Inc.|Collaborative Database Operations|
    KR101746049B1|2010-11-18|2017-06-28|삼성전자 주식회사|Method and apparatus for providing content in mobile terminal|
    US20120144123A1|2010-12-01|2012-06-07|International Business Machines Corporation|Read-ahead processing in networked client-server architecture|
    US8312096B2|2010-12-08|2012-11-13|Google Inc.|Priority inbox notifications and synchronization for mobile messaging application|
    KR101947199B1|2010-12-31|2019-02-12|이베이 인크.|Methods and systems for displaying content on multiple networked devices with a simple command|
    WO2012099617A1|2011-01-20|2012-07-26|Box.Net, Inc.|Real time notification of activities that occur in a web-based collaboration environment|
    US8799385B2|2011-03-31|2014-08-05|Loment, Inc.|Delivery control for email communicated among multiple end user communication devices|
    US8825842B2|2011-04-28|2014-09-02|Facebook, Inc.|Managing notifications pushed to user devices|
    CN102801755B|2011-05-27|2016-03-23|腾讯科技（深圳）有限公司|A kind of management method of application and a kind of application platform|
    US20160004410A1|2011-06-27|2016-01-07|Google Inc.|Processing Cursor Movements for Predictive Fetching|
    US8874669B2|2011-08-12|2014-10-28|Sony Corporation|Synchronizing messages on connected devices|
    US8788881B2|2011-08-17|2014-07-22|Lookout, Inc.|System and method for mobile device push communications|
    US20130067035A1|2011-09-08|2013-03-14|Bubble Ads Holdings Llc|System and method for cloud based delivery and display of content on mobile devices|
    US8799406B1|2011-09-14|2014-08-05|West Corporation|Method and apparatus of providing notification services to smartphone devices|
    US8639754B2|2011-09-30|2014-01-28|Advanced Messaging Technologies, Inc.|System and method for providing a protocol for message data|
    US8688793B2|2011-11-08|2014-04-01|Blackberry Limited|System and method for insertion of addresses in electronic messages|
    US8990307B2|2011-11-16|2015-03-24|Box, Inc.|Resource effective incremental updating of a remote client with events which occurred via a cloud-enabled platform|
    GB2497076A|2011-11-23|2013-06-05|Skype|Delivering only selected communication events to a user terminal or to a user|
    US9324055B2|2011-12-08|2016-04-26|Microsoft Technology Licensing, Llc|Techniques to manage remote events|
    US9811595B2|2011-12-21|2017-11-07|Yahoo Holdings, Inc.|Missed media system and method|
    US20130173742A1|2011-12-28|2013-07-04|United Video Properties, Inc.|Systems and methods for latency-based synchronized playback at multiple locations|
    US20130194172A1|2012-01-30|2013-08-01|Cellco Partnership D/B/A Verizon Wireless|Disabling automatic display shutoff function using face detection|
    EP2631743B1|2012-02-24|2018-05-02|BlackBerry Limited|Handheld device with notification message viewing|
    US8739249B1|2012-03-08|2014-05-27|Google Inc.|Push notifications for web applications and browser extensions|
    US8559924B1|2012-04-16|2013-10-15|At&T Intellectual Property I, L.P.|Method and apparatus for mobile device security|
    US9152204B2|2012-07-17|2015-10-06|Google Inc.|System wakeup based on changes in physical environment|US10013053B2|2012-01-04|2018-07-03|Tobii Ab|System for gaze interaction|
    US10394320B2|2012-01-04|2019-08-27|Tobii Ab|System for gaze interaction|
    US10488919B2|2012-01-04|2019-11-26|Tobii Ab|System for gaze interaction|
    US10540008B2|2012-01-04|2020-01-21|Tobii Ab|System for gaze interaction|
    US9560001B1|2012-04-02|2017-01-31|Google Inc.|Managing notifications across services|
    US20140047019A1|2012-08-07|2014-02-13|James Dean Midtun|Communication Alerts Management|
    US9491251B2|2012-11-27|2016-11-08|Facebook, Inc.|Transmission of notifications to multiple devices associated with a user|
    US9338403B2|2013-01-23|2016-05-10|Google Inc.|Persistent conversations|
    US9270630B1|2013-01-23|2016-02-23|Google Inc.|Integrating communication modes in persistent conversations|
    US9253223B1|2013-01-23|2016-02-02|Google Inc.|Live interaction in persistent conversations|
    US9742711B2|2013-03-15|2017-08-22|Sorenson Ip Holdings, Llc|Communication systems and related methods for notifying devices having a plurality of unique identifiers about missed communications|
    US9294423B2|2013-03-15|2016-03-22|Sorenson Communications, Inc.|Communication systems and related methods for notifying devices having a plurality of unique identifiers about missed communications|
    CN103313216B|2013-06-24|2015-04-01|腾讯科技（深圳）有限公司|Message prompt method, system and device for communication account|
    US9450904B2|2013-07-15|2016-09-20|Dropbox, Inc.|Coordinated notifications across multiple channels|
    US20150074195A1|2013-09-09|2015-03-12|Qualcomm Incorporated|Increasing power savings through intelligent synchronizing of data|
    KR102211535B1|2013-11-11|2021-02-03|삼성전자주식회사|Method and computer readable recording medium for managing a transmission message in a messsenger service|
    US8738723B1|2013-12-10|2014-05-27|Google Inc.|Predictive forwarding of notification data|
    US9537812B2|2013-12-31|2017-01-03|Google Inc.|Methods, systems, and media for managing notifications directed to multiple applications installed on a user device|
    EP3127060A1|2014-03-31|2017-02-08|PCMS Holdings, Inc.|System and method for updating notifications across devices and applications|
    US9794355B2|2014-04-08|2017-10-17|Samsung Electronics Co., Ltd.|Systems and methods for adaptive notification networks|
    US9750084B2|2014-04-30|2017-08-29|Samsung Electronics Co., Ltd.|Apparatus, method, and system for desynchronizing notifications across multiple devices|
    WO2015178562A1|2014-05-23|2015-11-26|Samsung Electronics Co., Ltd.|Method and apparatus for providing notification|
    US9629120B2|2014-05-23|2017-04-18|Samsung Electronics Co., Ltd.|Method and apparatus for providing notification|
    US9622214B2|2014-05-23|2017-04-11|Samsung Electronics Co., Ltd.|Method and apparatus for providing notification|
    US10638452B2|2014-05-23|2020-04-28|Samsung Electronics Co., Ltd.|Method and apparatus for providing notification|
    RU2580438C2|2014-09-02|2016-04-10|Общество С Ограниченной Ответственностью "Яндекс"|Methodof processing incoming electronic message and the server |
    CN105991412B|2015-02-12|2019-03-19|阿里巴巴集团控股有限公司|Information push method and device|
    US9727201B2|2015-04-01|2017-08-08|Microsoft Technology Licensing, Llc|Contextual help|
    US9876872B1|2015-04-03|2018-01-23|Symantec Corporation|Method or mechanism for self notification avoidance|
    US10425372B2|2015-08-18|2019-09-24|Google Llc|Notification targeting based on downstream user engagement|
    US9756005B2|2015-11-04|2017-09-05|Google Inc.|Notification bundles for affinities between notification data|
    US10489492B2|2015-12-10|2019-11-26|Dropbox, Inc.|Sending feature-instruction notifications to user computing devices|
    US10552234B2|2015-12-10|2020-02-04|Microsoft Technology Licensing, Llc|Enhanced notification of editing events in shared documents|
    US10069697B2|2016-01-29|2018-09-04|Microsoft Technology Licensing, Llc|Routing actions to user devices based on a user graph|
    US10893113B2|2016-06-06|2021-01-12|International Business Machines Corporation|Generating push notifications|
    US20170373997A1|2016-06-22|2017-12-28|International Business Machines Corporation|Reducing already viewed content in social networks|
    US10776320B2|2016-07-20|2020-09-15|International Business Machines Corporation|Avoiding redundant presentation of content|
    CN106657329A|2016-12-21|2017-05-10|北京奇虎科技有限公司|Mobile terminal as well as notification information control method and device|
    US10511564B2|2017-01-20|2019-12-17|Salesforce.Com, Inc.|User availability aware communication system|
    US10594815B2|2017-04-03|2020-03-17|Salesforce.Com, Inc.|Systems and methods for electronic notification broadcasts|
    US10812435B2|2018-02-28|2020-10-20|Ringcentral, Inc.|Systems and methods for suppressing repetitive notifications about messages in messaging groups|
    US10575123B1|2019-02-14|2020-02-25|Uber Technologies, Inc.|Contextual notifications for a network-based service|
    法律状态:
    2015-08-11| B03A| Publication of a patent application or of a certificate of addition of invention [chapter 3.1 patent gazette]|
    2018-12-04| B06F| Objections, documents and/or translations needed after an examination request according [chapter 6.6 patent gazette]|
    2020-04-14| B06U| Preliminary requirement: requests with searches performed by other patent offices: procedure suspended [chapter 6.21 patent gazette]|
    2020-09-01| B09A| Decision: intention to grant [chapter 9.1 patent gazette]|
    2020-12-15| B16A| Patent or certificate of addition of invention granted|Free format text: PRAZO DE VALIDADE: 20 (VINTE) ANOS CONTADOS A PARTIR DE 31/05/2013, OBSERVADAS AS CONDICOES LEGAIS. |
    优先权:
    申请号 | 申请日 | 专利标题
    US13/485.221|2012-05-31|
    US13/485,221|US10210480B2|2012-05-31|2012-05-31|Avoiding a redundant display of a notification on multiple user devices|
    [返回顶部]